Forum Activity for @michael

Updating the Documentation Module

Using Jamroom

Depends on how you've done the customized templates.

If you've cloned a skin or created a new one, then uploaded files that start with the name of the module:
/skins/xxYourSkin/jrDoc_category_index.tpl

Then they are safe, you'll just have the old version of the template file that you'll then need to check to see if there are any changes you want to bring in to your skin override template.

If you're over-riding by using the Template editor on the TEMPLATES tab of the Docs module in the ACP then those overrides will still be there after the update and you can use the COMPARE button to see what the difference is.

RSS Template Variables

Design and Skin Customization

Try:

RSS Template Variables

Design and Skin Customization

try:

RSS Template Variables

Design and Skin Customization

Things are getting to cryptic for me, im not understanding. What do you want to get into the rss.tpl file?

You want to get the profile info out.

Could you post your ideal RSS structure here along with the current structure and what info you need. Cheers.

--edit--
and whats the URL (or example of) that you're accessing the rss on. is it the main site feed or a profile.
updated by @michael: 08/23/19 08:16:57PM

RSS Template Variables

Design and Skin Customization

What variables you have available in a template can be discovered with {debug}

Docs: "{debug}"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1477/debug

one thing i DO NOT like about the new editor

Suggestions

Fix will be in JR6.4.0 which is getting released soon.

RSS Template Variables

Design and Skin Customization

You use a foreach loop to loop over the elements in an array, so if you have an array like this:
then a foreach loop over it would go

But if your array looks like this
Then the foreach loop would look like this


So it depends on what your array looks like as to how you access it outside a loop.

For the second array you can go
or

to get Simons pet.
updated by @michael: 08/22/19 10:16:57PM

one thing i DO NOT like about the new editor

Suggestions

The fix is going to be adding:
into
jrCore/form_editor.tpl
jrSiteBuilder/form_editor.tpl

The cause of the issue is the 'link' plugin:
https://www.tiny.cloud/docs/plugins/link/

and the 'contextmenu'
https://www.tiny.cloud/docs/ui-components/contextmenu

Since you can always link anything 'link' is turning up all the time. Even when what you want is really spellcheck.

Thanks for reporting this.

one thing i DO NOT like about the new editor

Suggestions

Yeah, you're right. Where did that come from....

I'll see if I can get it back to what it was.

Thanks.

ALLOW_ALL_DOMAINS missing

Installation and Configuration

You'd need to setup a page on your site that contains your player then embed that player in the other site using an iframe.

--edit--
Add a new page to your site by adding a .tpl file to your skin (or a clone of an existing skin), eg:
/skins/YOUR-SKIN/somename.tpl

That will can be accessed by going to
your-site.com/somename

and everything you add after that as parameters will be available in the {$_post} variable. so if you had
your-site.com/somename/song_id=55

Then you could get the value of song_id via the variable {$_post.song_id}.

You can use this to pass into the {jrCore_list} (the get stuff from the database function for any jamroom datastore.)

eg:


Then take a look at how the item_detail.tpl file of the jrAudio module does it to setup a player.

updated by @michael: 08/20/19 09:44:26PM